Skip to content

fix(deps): update tfo-go to v2.4.2 for Go 1.27 (Windows crash) - #162

Merged
hiddify-com merged 1 commit into
mainfrom
fix/tfo-go-go127
Oct 29, 2026
Merged

hiddify-com merged 1 commit into
mainfrom
fix/tfo-go-go127

Conversation

@veto9292

Copy link
Copy Markdown
Collaborator

Problem

On Windows the core crashed with large subscriptions, usually within a second of starting (nil pointer dereference in net.(*OpError).Error or errors.As).

The cause is TCP Fast Open. tfo-go v2.3.2 links to Go's internal internal/poll.(*FD).execIO with an older signature (buf []byte), but Go 1.27.3 takes pinPtrs ...any. When a dial or handshake through TCP Fast Open failed, the returned error was broken, and the core crashed as soon as it read it.

Fix

tfo-go v2.4.2, which matches Go 1.27.3. golang.org/x/sys goes to v0.49.0, which it requires.

Test

  • Profile of about 6,000 proxies with tcp_fast_open.
  • Before: the CLI crashed in 1 s.
  • After: it ran without a crash, and failed dials (refused, timeout, TLS errors) were logged normally.
  • Also checked in the Windows app.

🤖 Generated with Claude Code

On Windows, tfo-go v2.3.2 links to internal/poll.(*FD).execIO with the
signature of an older Go (a buf []byte last argument). Go 1.27.3 takes
pinPtrs ...any there, so with TCP Fast Open a failed dial or handshake
returned a broken error, and the core crashed as soon as it read it (in
the URL test's log, or in errors.As in the TLS dialer). Large
subscriptions crashed within a second of starting.

v2.4.2 matches Go 1.27.3. With the same 6,000-proxy profile the core
ran without a crash, and failed dials through TCP Fast Open (refused,
timeout, TLS errors) were logged normally. golang.org/x/sys moves to
v0.49.0, which tfo-go v2.4.2 requires.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hiddify-com
hiddify-com merged commit dfe3b39 into main Oct 29, 2026
4 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants